Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

Ensuring a small transaction size

One of the main advantages of using normal 4GL transactions on the AppServer is their small scope, requiring no communication with the client for the AppServer transaction to complete. In general, to implement a normal 4GL transaction in an AppServer procedure, you follow the same programming practices as when writing a small-scoped transaction for a Progress 4GL client.

In particular, avoid including code that can block the AppServer agent or otherwise delay execution, such as:

Writing to or reading from external files.
Invoking any other operating system calls (for example, the OS-COMMAND statement).

For more information on implementing transactions in a Progress 4GL procedure, see OpenEdge Development: Progress 4GL Handbook .